The npm scope needs a publishable package name under @imdeadpool while preserving the user-facing colony binary. Update package metadata, root scripts, install docs, and e2e pack checks so the release tarball is named and verified as @imdeadpool/colony-cli without changing runtime behavior.

Constraint: npm package @imdeadpool/colony-cli is unpublished and @imdeadpool/colony-cli@0.5.0 dry-run succeeds.

Rejected: Rename the binary with the package name | existing CLI command remains colony for users.

Confidence: high

Scope-risk: narrow

Directive: Do not rename the colony binary when changing npm package metadata without checking install docs and e2e pack scripts.

Tested: pnpm --filter @imdeadpool/colony-cli test; pnpm --filter @imdeadpool/colony-cli pack:release; npm --cache /tmp/agents-hivemind-npm-cache publish apps/cli/release --dry-run --access public

Not-tested: Real npm publish completed; npm requires OTP/browser authentication (EOTP).